BARRIERS TO IMPLEMENTATION OF ERM SYSTEMS IN LARGE ENTERPRISES

Enterprises operating in the modern world should lay particular emphasis on increasing the security of functioning, which is possible thanks to the effective and integrated risk management. However, it should be noted the existence of a number of barriers making the implementation of ERM difficult, arising for large enterprises, primarily from the lack of sufficient competence, knowledge, or experience

He role of funeral director

In general, the public not only in the UK, but in the world, has very limited knowledge of the funeral industry, yet feels easy to criticize it or judge the ones employed, and associateted with the funeral industry. Unknown but, nevertheless, inherently stigmatized role of the funeral director is investigated. Identifying managerial issues in the course of researching the chosen area of study allowed authors to recognize the conflict between the empowered funeral director and disadvantaged, by the virtue of distress purchase, bereaved customer

Handling Complexity in Modern Software Engineering: Editorial Introduction to Issue 32 of CSIMQ

The potential of the Internet and related digital technologies, such as the Internet of Things (IoT), cognition and artificial intelligence, data analytics, services computing, cloud computing, mobile systems, collaboration networks, and cyber-physical systems, are both strategic drivers and enablers of modern digital platforms with fast-evolving ecosystems of intelligent services for digital products. This issue of CSIMQ presents three recent articles on modern software engineering. First, we focus on continuous software development and place it in the context of software architectures and digital transformation. The first contribution is followed by the description of the basis of specific security requirements and adequate digital monitoring mechanisms. Finally, we present a practical example of the digital management of livestock farming

Za uporabo Light verzije UML 2.x-a: ocena in vzorec

UML 2.x version has become an even more complicated and diverse set of graphical techniques than its predecessors. Therefore, system developers propose preparation of its reduced, limited or minimal version called Light UML. This problem has become also a serious challenge for the UML academic teachers. The goal of this paper is the study of specifying the UML 2.x Light version content on the basis of the questionnaire survey registering opinions of 180 university students of the University of Gdansk. After the introduction, the methodological prerequisites of the survey are clarified. Then, the research results are presented and discussed according to seven essential UML diagrams assessment criteria, included in a questionnaire. The final UML 2.x version, resulting from the accomplished survey, is exposed in the last part of the paper.UML 2.x verzija je postala celo bolj zapleten in raznolik skupek grafičnih tehnik kot njeni predhodniki. Zato sistemski razvijalci predlagajo razvoj zmanjšane, omejene ali minimalne verzije imenovane Light UML. Ta problem predstavlja tudi resen izziv za akademske kroge, ki se ukvarjajo s poučevanjem UML. Namen tega prispevka je preučitev in opredelitev vsebine UML 2.x Light verzije na osnovi ankete, s katero smo zbrali mnenja 180 študentov na Univerzi v Gdansku. Uvodu sledi razlaga metodoloških zahtev raziskave. Zatem so predstavljeni rezultati, ki so interpretirani skladno s sedmimi bistvenimi ocenjevalnimi kriteriji UML diagramov, ki so bili vključeni v anketo. Končna UML 2.x verzija, ki izhaja iz izvedene raziskave, je razložena v zadnjem delu prispevka

Agile software development approach for \u27ad-hoc\u27 IT projects

Restrictive Scrum assumptions make the effectiveness of this approach debatable in projects deviating from typical execution conditions. This article delivers a comprehensive software development approach for both academic and commercial Information Technology (IT) projects effectuated by teams that are hampered by significantly unsystematic participation of project members and mercurial internal communication. The nature of ‘ad-hoc’ projects imposes another level of difficulty in terms of both managing the conduct of such a project and ensuring the quality of the end product. Multicyclic action research enabled a gradual adaptation of the Scrum approach to support such project conditions. This study introduces major alterations to Sprint implementation and minor enhancements within the documentation process to streamline knowledge sharing among Development Team members. Proposed key alterations include the evolution of Daily Scrum towards Weekly Scrum, the possibility of extending Sprints length, the eventuality to switch team members during Sprint due to substantial failure to meet deadlines, having at least two team members responsible for a single Product Backlog Item (PBI) at all times, as well as exclusion of Burndown Chart in favor for Development Team members updating their working time. Positive validation of enhancements in mixed settings confirms that the generic Scrum framework can be adapted to support highly volatile projects. The proposed approach is suitable not only for carrying out software development initiatives that rely heavily on the skills of external experts and/or volunteers. It also supports traditional Scrum teams that seek to reduce their exposure to risk arising from organizational changes

Poster: Drafting a General Framework for Systems Integration Delivery

In IT ecosystems that imply the exchange of data with systems on the customer or business partner side, it is oftentimes problematic or even borderline impossible to predict what external systems shall eventually be covered by integration and what technological solutions should be employed. Based on the feedback obtained in a series of interviews, we lay a foundation for building a framework for developing system integration. The framework enhances the research background in terms of technological specificity and constraints behind developing projects of this nature

Environmental, Social, and Corporate Governance. From Unascertainable Statements to Action Plan

Companies employ Environmental, Social, and Corporate Governance (ESG) reports to inform stakeholders on their activities and achievements regarding reducing carbon dioxide emissions and lowering electricity consumption. Whereas some frameworks for ESG reporting have been standardized, the capability to independently trace real actions undertaken leaves a lot to be desired. Despite the steady evolution of IT-powered analytics, the reliability of environmentally-targeted activity is still under threat due to the inability of translating publicity-targeted efforts into quantifiable measures. This short paper constitutes an attempt to lay foundations for backing up pro-ecological ESG statements with a realistic and validated action plan. To achieve this, a 3-cycled Participatory Action Research effort is being undertaken jointly with the staff of a Central European insurance group headquartered in Poland, EU. The paper outlines the research gap, the specific research design of the ongoing empirical study as well as the expected outcomes of the research endeavor

Agile software development approach for 'ad-hoc' IT projects

Restrictive Scrum assumptions make the effectiveness of this approach debatable in projects deviating from typical execution conditions. This article delivers a comprehensive software development approach for both academic and commercial Information Technology (IT) projects effectuated by teams that are hampered by significantly unsystematic participation of project members and mercurial internal communication. The nature of ‘ad-hoc’ projects imposes another level of difficulty in terms of both managing the conduct of such a project and ensuring the quality of the end product. Multicyclic action research enabled a gradual adaptation of the Scrum approach to support such project conditions. This study introduces major alterations to Sprint implementation and minor enhancements within the documentation process to streamline knowledge sharing among Development Team members. Proposed key alterations include the evolution of Daily Scrum towards Weekly Scrum, the possibility of extending Sprints length, the eventuality to switch team members during Sprint due to substantial failure to meet deadlines, having at least two team members responsible for a single Product Backlog Item (PBI) at all times, as well as exclusion of Burndown Chart in favor for Development Team members updating their working time. Positive validation of enhancements in mixed settings confirms that the generic Scrum framework can be adapted to support highly volatile projects. The proposed approach is suitable not only for carrying out software development initiatives that rely heavily on the skills of external experts and/or volunteers. It also supports traditional Scrum teams that seek to reduce their exposure to risk arising from organizational changes